| | 65 | |
| | 66 | |
| | 67 | == XMPP (Jabber) Protocol == |
| | 68 | |
| | 69 | === How do I choose which XMPP server to use or configure an XMPP account? === |
| | 70 | The XMPP server is part of your XMPP ID. For example, the ID `foo@bar.com`, bar.com would be the server to use. When entering your XMPP account information into Pidgin, specify everything ''before'' the `@` in the Screen name field and everything ''after'' the `@` in the Domain field. |
| | 71 | |
| | 72 | === What is the "Resource" field for in the account editor? === |
| | 73 | The resource field specifies the XMPP resource you are using. The use of unique resources allows you to connect to your XMPP server from multiple locations simultaneously. Resources might have meaningful names, such as Home, Work, Mobile, etc., or something else entirely that you choose. Pidgin defaults to a resource of Home. |
| | 74 | |
| | 75 | === How do I change my resource string? === |
| | 76 | Go to Accounts->Add/Edit. Find your XMPP account and uncheck the Enabled box. Select the account and click Modify. Change the string in the Resource field. |
| | 77 | |
| | 78 | === How can I configure resource priority? === |
| | 79 | Pidgin does not currently support this. You will need to configure resource priority with another XMPP client. Pidgin will, however, honor any resource priorities that have been configured. |
| | 80 | |
| | 81 | === What does "Cancel Presence Notification" do? === |
| | 82 | See the next question. |
| | 83 | |
| | 84 | === How can I deauthorize a buddy from seeing my status? === |
| | 85 | Right-click the buddy on the buddy list and select Cancel Presence Notification. Note that the buddy will have to request authorization again to be able to see your presence. |
| | 86 | |
| | 87 | === What does "Unsubscribe" do? === |
| | 88 | If you select "Unsubscribe" from the menu presented when right-clicking an XMPP buddy, you will no longer see that buddy's presence. You will need to re-request authorization to resume seeing the buddy's presence. |
| | 89 | |
| | 90 | === How do I remove a buddy from my roster? === |
| | 91 | Right-click the buddy and click Remove. |
| | 92 | |
| | 93 | == Yahoo!(Y!M) Protocol == |
| | 94 | |
| | 95 | === How do I get blocking someone to work? === |
| | 96 | There is a known bug in the Yahoo! protocol code present in libpurple. We've been unable to determine the exact cause or a workable code solution to the problem, but the failure seems to be most prominent when the blocking code tries to automatically remove the buddy from your list (this is required for a block on Yahoo!). It will also ''always'' fail if libpurple thinks the buddy is already blocked. |
| | 97 | |
| | 98 | We suggest manually removing Yahoo! buddies before attempting to block them. For buddies reported as already blocked who are not in fact blocked, unblock them (in Tools->Privacy) and block them again. This works often. |
| | 99 | |
| | 100 | === Why can't I connect to Yahoo! from behind a firewall or NAT? === |
| | 101 | Your firewall or NAT is not allowing YMSG packets (packets for the Yahoo! protocol) to pass through it. You can try changing the port Pidgin attempts to connect to. Go to Tools->Edit, find your Yahoo! account, uncheck the Enabled box, then select the account and click Modify. On the Advanced tab, change the value in the Pager port field. Ports known to work are 20, 23, 25, 80, 119, 5050, 8001, and 8002. This will not work for all users, but does help many. |
| | 102 | |
| | 103 | === Why doesn't Pidgin have the official client's "Firewall with no proxy" option? === |
| | 104 | The official client's Firewall with no proxy option wraps the Yahoo! YMSG protocol in HTTP, which enables it to pass through many firewalls and NATs that filter IM traffic but not HTTP traffic. Pidgin and libpurple currently do not support this. |
| | 105 | |
| | 106 | === Can I get a list of Yahoo! chatrooms? What about localized lists? === |
| | 107 | Tools->Room List will let you list available Yahoo! chat rooms. Yahoo! has currently disabled user-created rooms. The option to create rooms still exists in Pidgin but will be non-functional until Yahoo! re-enables user-created rooms. |
| | 108 | |
| | 109 | By default the room list shows US-localized chat rooms. To get a localized room list for another locale, you'll need to change the Chat Room Locale setting in the account editor, on the Advanced tab. Enter a country code in this field. Certain country codes no longer seem to work (most notably de). The list of known-working country codes was at last check the following: |
| | 110 | * aa -> Asia |
| | 111 | * ar -> Argentina |
| | 112 | * au -> Australia |
| | 113 | * br -> Brazil |
| | 114 | * ca -> Canada |
| | 115 | * cf -> Central African Republic |
| | 116 | * cn -> China |
| | 117 | * dk -> Denmark |
| | 118 | * es -> Spain |
| | 119 | * fr -> France |
| | 120 | * hk -> Hong Kong |
| | 121 | * in -> India |
| | 122 | * it -> Italy |
| | 123 | * kr -> Korea, Republic of |
| | 124 | * mx -> Mexico |
| | 125 | * no -> Norway |
| | 126 | * se -> Sweden |
| | 127 | * sg -> Singapore |
| | 128 | * tw -> Taiwan |
| | 129 | * uk -> United Kingdom |
| | 130 | * us -> United States of America |
| | 131 | |
| | 132 | If you discover any of these no longer work, or find other country codes that do work, please don't hesitate to contact the development team. |
| | 133 | |
| | 134 | === What protocol does Pidgin use to connect to Yahoo!? === |
| | 135 | Normally Pidgin uses the YMSG protocol, which is the same protocol that the official Yahoo! clients use, although Pidgin uses a slightly older version of the protocol than current official clients. If an attempt to login returns the "Invalid Password" error code, Pidgin automatically tries to log in using the "!WebMessenger" method. This method still uses the YMSG protocol, but authenticates differently, and connects to a different server. |
| | 136 | |
| | 137 | While in Web Messenger mode, several things work differently or not at all. Adding, moving, and removing buddies doesn't work, and the only available statuses are "Available" and "Invisible". In addition, the Yahoo! server seems to ignore all Yahoo! Chat related packets. For this reason, we use the YCHT protocol to join Yahoo! Chat rooms while connected using the Web Messenger method. |
